keep the args sorted :-)

keep the args sorted :-)

Oops, fixed now.

ImportError: No module named setuptools

Humm, is that a flake?

/retest

/lgtm

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: krzyzacy, MrHohn

The full list of commands accepted by this bot can be found here.

From https://k8s-testgrid.appspot.com/kubernetes-presubmits#pull-kubernetes-e2e-gke-gpu I see empty history. How do I verify it is not failing and who usually triggers this job?

I'm not sure who usually triggers it but it is manually triggered which is why the history is empty. The GCE GPU job is used normally AFAIK.

for presubmit, testgrid only displays one day's history... which means no body triggered the job yesterday :-)

Here's the history for the job: https://k8s-gubernator.appspot.com/builds/kubernetes-jenkins/pr-logs/directory/pull-kubernetes-e2e-gke-gpu

Thanks folks. Also bad news, just realized that the custom network feature might not work on GKE. We should choose a GCE PR job to start with..

@MrHohn how about pull-kubernetes-e2e-gce-gpu? :-)

Do GPU jobs have an official guinea pig status now? :-P

Or we can create a dummy job and then delete it later

@mindprince or we should make gpu job blocking :-)

Or we can create a dummy job and then delete it later

I've tested the custom network feature on all auto-run PR jobs on kubernetes/kubernetes#52377 for couple times (by temporarily setting CREATE_CUSTOM_NETWORK=true) and they all looked fine. We will be able to gain more confidence if we canary it on an auto-run PR job.

Also vote for pull-kubernetes-e2e-gce-gpu, but let's make the change (or decision) tomorrow morning in case it will break :)